Skip to content

Conversation

@hypery2k
Copy link
Contributor

Potential fix for https://github.com/CloudTooling/dev-buildbox/security/code-scanning/1

To fix the problem, add a permissions block to restrict the GITHUB_TOKEN permissions. The best way is to set the permissions at the top-level of the workflow so they apply to all jobs by default. Based on the workflow, the jobs interact only with the repository code and external Docker registries via secrets, so the minimal required permission is contents: read. There is no evidence that the jobs require other elevated permissions (such as issues: write or pull-requests: write). The change should be made at the very top of .github/workflows/build.yml after the name field and before the on block.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

…n permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
@hypery2k hypery2k closed this Oct 24, 2025
@hypery2k hypery2k deleted the alert-autofix-1 branch October 24, 2025 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants